Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NullPointerException in IndexShardRoutingTable.getActiveAttribute #4589

Closed
karol-gwaj opened this issue Jan 2, 2014 · 1 comment
Closed

NullPointerException in IndexShardRoutingTable.getActiveAttribute #4589

karol-gwaj opened this issue Jan 2, 2014 · 1 comment
Assignees
@s1monw
Labels
>bug v0.90.10 v1.0.0.RC1

Comments

@karol-gwaj
Copy link

im getting error below after killing one node in the cluster
(exception is thrown on remaining nodes)

org.elasticsearch.common.util.concurrent.UncategorizedExecutionException: Failed execution
        at org.elasticsearch.action.support.AdapterActionFuture.rethrowExecutionException(AdapterActionFuture.java:90)
        at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:49)
        at org.elasticsearch.action.ActionRequestBuilder.get(ActionRequestBuilder.java:67)
        ...
Caused by: java.util.concurrent.ExecutionException: java.lang.NullPointerException
        at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.getValue(BaseFuture.java:288)
        at org.elasticsearch.common.util.concurrent.BaseFuture$Sync.get(BaseFuture.java:275)
        at org.elasticsearch.common.util.concurrent.BaseFuture.get(BaseFuture.java:113)
        at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:45)
        ... 15 more
Caused by: java.lang.NullPointerException
        at org.elasticsearch.cluster.routing.IndexShardRoutingTable.getActiveAttribute(IndexShardRoutingTable.java:441)
        at org.elasticsearch.cluster.routing.IndexShardRoutingTable.preferAttributesActiveInitializingShardsIt(IndexShardRoutingTable.java:488)
        at org.elasticsearch.cluster.routing.IndexShardRoutingTable.preferAttributesActiveInitializingShardsIt(IndexShardRoutingTable.java:483)
        at org.elasticsearch.cluster.routing.operation.plain.PlainOperationRouting.preferenceActiveShardIterator(PlainOperationRouting.java:169)
        at org.elasticsearch.cluster.routing.operation.plain.PlainOperationRouting.getShards(PlainOperationRouting.java:80)
        at org.elasticsearch.action.get.TransportGetAction.shards(TransportGetAction.java:80)
        at org.elasticsearch.action.get.TransportGetAction.shards(TransportGetAction.java:42)
        at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.<init>(TransportShardSingleOperationAction.java:121)
        at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction$AsyncSingleAction.<init>(TransportShardSingleOperationAction.java:97)
        at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:74)
        at org.elasticsearch.action.support.single.shard.TransportShardSingleOperationAction.doExecute(TransportShardSingleOperationAction.java:49)
        at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:63)
        at org.elasticsearch.client.node.NodeClient.execute(NodeClient.java:92)
        at org.elasticsearch.client.support.AbstractClient.get(AbstractClient.java:179)
        at org.elasticsearch.action.get.GetRequestBuilder.doExecute(GetRequestBuilder.java:112)
        at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85)
        at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59)

context:

  • version: 0.90.9
  • 3 node cluster
  • 2 replicas
  • 10 shards per index
@ghost ghost assigned s1monw Jan 3, 2014
@s1monw s1monw mentioned this issue Jan 3, 2014
Closed
s1monw added a commit to s1monw/elasticsearch that referenced this issue Jan 3, 2014
@s1monw
Check if node is still present when collecting attribute shard routings
0af78bd 
The node we need to lookup for attribute colelction might not be part
of the `DiscoveryNodes` anymore due to node failure or shutdown. This
commit adds a check and removes the shard from the iteration.

Closes elastic#4589
@s1monw
Copy link
Contributor

s1monw commented Jan 3, 2014

thanks for reporting this! I will push a fix soonish

s1monw added a commit that referenced this issue Jan 3, 2014
@s1monw
Check if node is still present when collecting attribute shard routings
71672ed 
The node we need to lookup for attribute colelction might not be part
of the `DiscoveryNodes` anymore due to node failure or shutdown. This
commit adds a check and removes the shard from the iteration.

Closes #4589
@s1monw s1monw closed this as completed in 65c4282 Jan 3, 2014
brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
@s1monw @brusic
Check if node is still present when collecting attribute shard routings
2ccb81d 
The node we need to lookup for attribute colelction might not be part
of the `DiscoveryNodes` anymore due to node failure or shutdown. This
commit adds a check and removes the shard from the iteration.

Closes elastic#4589
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@s1monw
Check if node is still present when collecting attribute shard routings
a21434f 
The node we need to lookup for attribute colelction might not be part
of the `DiscoveryNodes` anymore due to node failure or shutdown. This
commit adds a check and removes the shard from the iteration.

Closes elastic#4589
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@s1monw s1monw

Labels
>bug v0.90.10 v1.0.0.RC1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check if node is still present when collecting attribute shard routings s1monw/elasticsearch
2 participants
@s1monw @karol-gwaj